This help topic covers the how to properly process a Batch.
After you create a batch and enter transactions, go to the Batch Profile page to preprocess the batch, This determines whether the batch can be closed. During this process netFORUM goes through the batch and checks for issues, primarily common setup errors, that may exist.
Example: one sided entries, missing G/L Account Numbers, etc.
If the system finds any exceptions in the batch, the Exception Report icon and Exception Go To icons will activate. After you fix all of the issues — REMEMBER TO PREPROCESS THE BATCH AGAIN!
To Preprocess a Batch:
The next step is to correct any Batch Exceptions.
This shows all of the debits and credits to the G/L Accounts for this batch. This can be printed out and attached to your batch as needed.
To View a Batch Report, click the batch report icon on the Batch Profile page.
The Batch Report includes the following information:
An exception will occur during the Batch Close process if you NEGLECT to:
After you have initiated the pre-process, if there are issues with information in the batch, the exception report and exception Goto icons will be ACTIVATED.
To View and a Batch Exception Report, click the exception report icon. The Batch Exceptions page displays describing the exceptions.
To Edit the Exception:
After the exceptions are processed, the next step is closing the batch.
Click exception goto icon to display the exceptions. This will give you the ability to go directly to the record in question.
Common Issue: The default overpayment liability account has not been set up on the Business Unit and someone overpaid an invoice. There is no account for the credit that has been created. Simply going to the Business Unit, adding that default account and pre-processing again will resolve the issue.
Before you can post a batch, the Batch Total Amount must equal the Batch Control Total and the Batch Total Count must equal the Control Total Count. If they don't match, you must review the totals and make the appropriate corrections before you can close the batch.
The Control Total Count can be used to verify the Batch Total Amount, to ensure that the transaction information was entered accurately.
To Edit a Batch:
When you finish adding transactions, pre-processing the batch, and correcting batch exceptions, click the close batch icon to close the batch.
Closing the Batch means that all control totals and amounts have been verified and that the transactions are ready to be entered into the journal. The original transactions can no longer be adjusted. To make an adjustment after this point, you must create a new transaction and add it to a new batch.
To Close a Batch:
The close date and closed by information should get updated with the current date and the user who closed the batch.
Important! PROFORMA INVOICES CANNOT BE EXPORTED! If you attempt to close a batch that includes a Proforma invoice, an exception will be created.
The next step is posting the batch.
Once the Batch has been closed, Posting a Batch transfers the transactions to the General Ledger (i.e., transactions are posted to the General Ledger by posting the batch that contains them). Depending on your business rules, you may post it once it is closed or post a number of batches at once. If you are using a third-party accounting system, for example, Great Plains, when you post a batch, the batch export file and summary are sent to Great Plains.
This process creates and exports files and displays the G/L Accounts under the Ledger profile tab. The export files can be saved and then imported into the General Ledger as needed.
See also Accounting Integrations for details on how netFORUM writes export files for different accounting systems.
Note: The batch is posted after you have added transactions to a batch, preprocessed the batch, corrected any batch exceptions, and closed the batch.
To Post a Batch:
Viewing the Batch Export Summary After you post a Batch, you can view the Batch Export Summary by clicking the Ledger tab on the Batch Profile. The Batch Export Summary shows one line item per account, per batch. It does not include any transaction specific information.
For customers who need to override the baseline batch selection list, the BatchesSelectionOverrideSP system option can be used to implement a custom batch process via a stored procedure. This batch is then used as the default batch site-wide.
Caution! Improperly formatted stored procedures can cause errors and loss of functionality to occur. Contact your Abila representative for assistance in setting up this feature.
Once this system option is set up, the custom batch process you provided to your account representative will appear site-wide instead of the baseline batch list.